<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
   <title>Content types in Eclipse</title>
<link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
</head>
<body text="#000000" bgcolor="#FFFFFF">
&nbsp;
<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
  <tr> 
    <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">
    Content types in Eclipse - details</font></font></b></td>
  </tr>
  <tr> 
    <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td>
    <td WIDTH="98%">
<p><b>Plan item</b></p>
      <p><i>&quot;Content-type-based editor lookup. The choice of editor is currently 
        based on file name pattern. This is not very flexible, and breaks down 
        when fundamentally different types of content are found in files with 
        undistinguished file names or internal formats. For example, many different 
        models with specialized editors get stored in XML format files named *.xml. 
        Eclipse should support a notion of content type for files and resources, 
        and use these to drive decisions like which editor to use. This feature 
        would also be used by team providers when doing comparisons based on file 
        type. The several existing file-type registries in Eclipse should be consolidated. 
        [Platform Core, Platform UI] [Theme: User experience] (bug <a
 href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=37668">37668</a>, <a
 href="http://dev.eclipse.org/bugs/show_bug.cgi?id=51791">51791</a>, <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=52784">52784</a>)&quot;</i></p>
      </td>
  </tr>
  
  <tr> 
    <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td>
    <td WIDTH="98%">
<p><b>Overview document</b></p>
      <p>An overview of the proposed solution is available <a href="../../documents/content_types.html">here</a>.</p>
      </td>
  </tr>
  <tr> 
    <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td>
    <td WIDTH="98%">
<p><b>Related bug reports</b></p>
      <p>A list of related bug reports is available <a href="https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=substring&short_desc=%5Bcontent+type%5D&product=Platform&component=Resources&component=Runtime">here</a>.</p>
     </td>
  </tr>  
  <tr> 
    <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td>
    <td> 
      <p><b>Current status</b></p>
      <p><em>May 5th, 2004</em></p>
      <p>Core content type infrastructure is being currently used by the new encoding support (Resources), 
      content-sensitive object contributions (UI) and structured content comparisons (Compare)</p>
      <p><em>April 28th, 2004</em></p>	  
      <p>The adoption of content types for editor lookup has been postponed for after 3.0. Core content type 
      infrastructure will be available for 3.0 (bug <a
 href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=60291">60291</a>)</p>
      <p><em>April 6th, 2004</em></p>	  
      <p><a href="../../documents/content_types.html">Proposal</a> was made available. </p>
      <p>Gathering feedback from the community.</p>
    </td>
  </tr>
</table>

</body>
</html>
